Add PDL constraint function ktdf.is_precision - #145
Closed
msdataei wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Masoud Ataei <Masoud.Ataei.Jaliseh@ibm.com>
Contributor
Author
|
Upstream changes are in PR#4682 |
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ktdf.is_precision, usable in device pattern rules to gate matches on the element precision of alinalg.genericop's output (fp16,fp32, orbf16).PatternCachealongside the existingktdf.is_reduction_kind/ktdf.is_inner_dim_reductionconstraints.Details
ktdfIsPrecisioninspects the first output of alinalg.genericop, resolves its element type (unwrappingMemRefType/ShapedTypeas needed), and compares it against a caller-suppliedexpected_precstring attribute. It fails the match if:linalg.generic,f16/f32/bf16.